-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Code fix to add DisableRuntimeMarshalling when required #67676
Code fix to add DisableRuntimeMarshalling when required #67676
Conversation
Implement code fix to provide the DisableRuntimeMarshalling attribute when a P/Invoke requires it. Update tool versions to get required bugfixes
…-marshalling-code-fix
Tagging subscribers to this area: @dotnet/interop-contrib Issue DetailsImplement code fix to provide the DisableRuntimeMarshalling attribute when a P/Invoke requires it. Update tool versions to get required bugfixes
|
...pServices/gen/LibraryImportGenerator/Analyzers/AddDisableRuntimeMarshallingAttributeFixer.cs
Outdated
Show resolved
Hide resolved
...pServices/gen/LibraryImportGenerator/Analyzers/AddDisableRuntimeMarshallingAttributeFixer.cs
Show resolved
Hide resolved
...e.InteropServices/gen/Microsoft.Interop.SourceGeneration/Marshalling/MarshallingGenerator.cs
Show resolved
Hide resolved
...es/tests/LibraryImportGenerator.UnitTests/AddDisableRuntimeMarshallingAttributeFixerTests.cs
Show resolved
Hide resolved
…-marshalling-code-fix
I'm seeing MethodAccessExceptions on Mono for these tests in the Roslyn SDK... I'll take a look, but I have a feeling that this is some deficiency in Mono with dynamic assemblies and it might be worth just disabling these new tests on Mono for now. cc @akoeplinger |
Implement code fix to provide the DisableRuntimeMarshalling attribute when a P/Invoke requires it.
Update tool versions to get required bugfixes